You are here: FAQ > Tips and Techniques > Archiving from z/OS

Archiving from z/OS

In earlier versions, indexes could be in DB2 but not the actual compressed data. This let you store indexes on the host, but the compressed data must be on the LAN. You could store compressed data on the host in flat files, but there was no client-server mechanism to retrieve the data from a workstation, and flat file access is not compatible with CICS.

In version 5.0 and in later versions, the compressed data could also be stored in DB2. Although this is still called archive, it differs from traditional archive, since data stored in DB2 is not permanent, and not as long-lived as it could be if it were stored on a high-volume optical drive. Depending on the DB2 tables and access rights, data could be changed or tables could be dropped.

The Client Application Enabler is an IBM product related to DB2 and DDCS which gives a thin version of DDCS on the client workstations and a fat gateway on a server-type machine. This allows each workstation to have less software than a pure DDCS solution.

From Documaker’s perspective, the system just talks to DB2. Therefore, it does not matter to the system if it is DDCS or CAE, as long as DB2 itself can get to the z/OS DB2 tables. This is independent of the Documaker system.